Conversation
buttplug/buttplug-device-config/device-config-v3/buttplug-device-config-v3.yml
Outdated
Show resolved
Hide resolved
| - 0 | ||
| services: | ||
| 0000ffe0-0000-1000-8000-00805f9b34fb: | ||
| tx: 0000ffe1-0000-1000-8000-00805f9b34fb No newline at end of file |
There was a problem hiding this comment.
I don't suppose you did any work to understand the touch slider readings?
There was a problem hiding this comment.
You're right. Syncbot also has Rx channel and can read battery level and slider, but this PR focuses on the core functionality. (This is just FYI question, right?)
There was a problem hiding this comment.
Pretty much. Ideally I'd ask for the protocol to be documented (both directions) in an issue on https://github.com/buttplugio/docs.buttplug.io just so we at least have the notes recorded so it'll be quicker to add sensor support later
There was a problem hiding this comment.
Sounds good. I have summarized the findings from my analysis in an issue.
blackspherefollower
left a comment
blackspherefollower
left a comment
There was a problem hiding this comment.
There's a couple of minor tweaks needed, but overall the fact you've worked out what the protocol is doing is a major achievement here.
I'll test with my hardware when I'm back home in a week.
|
So, I think this is in good shape (maybe run Thanks for your hard work on this one |
|
Hmm... Unfortunately mine isn't behaving with this implementation. |
|
That's unfortunate... One possibility is that the encryption key is generated based on information specific to a particular device (such as the MAC address). I'll do a deeper analysis when I have time. |
qdot
force-pushed
the
dev
branch
3 times, most recently
from
0f9713e to
e71d832
Compare
2 participants
Hello, I've added support for Syncbot, a new powerful sex toy.
The encrypt key is hardcoded. You must use the correct encrypt key for the protocol to work properly.
The implementation was tested using intiface-engine.